🌱 feat: Create an Explicit Default Workspace - #93

Make encoded storage names unambiguously distinct

When a valid ID contains :, the encoded result can itself be another valid ID that takes the unhashed branch. For example, vm:a and vm_a-2d4fcea9e21e004d both pass the bridge ID pattern and both map to vm_a-2d4fcea9e21e004d, so workers under the same home—or workspace IDs under one worker—can unexpectedly share the same persistent default workspace. Use disjoint encodings, such as hashing every value or prefixing encoded names.

Useful? React with 👍 / 👎.

Fixed in fbcba99. Default workspace components now use disjoint raw- and exact base64url encoded- namespaces, while the pre-existing bridge identity filename behavior remains unchanged. Added the reported collision pair as a regression test.

Treat an empty worker directory as absent

When LIBRECHAT_CODE_WORKER_DIR is exported as an empty or whitespace-only placeholder (or --worker-dir= is supplied), explicitWorkerDirectory becomes ''. The conflict check treats that as absent, but this nullish coalescing still selects it, so --default-workspace/LIBRECHAT_CODE_DEFAULT_WORKSPACE=true silently creates and registers no workspace. Normalize the empty value to undefined before choosing the default path.

Useful? React with 👍 / 👎.

Fixed in fbcba99. Worker-directory input is normalized so empty and whitespace-only CLI/environment values are absent and --default-workspace can select the application-owned path. The CLI integration test now covers a whitespace-only environment value.

Encode case to avoid aliases on case-insensitive filesystems

On case-insensitive filesystems such as the default macOS setup supported by this package, distinct valid IDs like VM-1 and vm-1 produce raw-VM-1 and raw-vm-1, which resolve to the same directory and can share persistent workspace contents under one home. Fresh evidence in this exact head is that the replacement raw- namespace still preserves letter case, while BRIDGE_WORKER_ID_PATTERN treats these IDs as distinct; use a case-independent encoding or digest for every component.

Useful? React with 👍 / 👎.

Fixed in 47d4832. Every default workspace component now uses a full lowercase SHA-256 digest, so case-insensitive filesystems cannot alias distinct case-sensitive IDs. Coverage includes the VM-1/vm-1 case-folded comparison.

Keep trimming configured worker directories

When LIBRECHAT_CODE_WORKER_DIR contains incidental leading or trailing whitespace, nonEmpty now verifies the trimmed value but returns the original string, so LocalWorkspaceTools.create calls realpath on a different path and rejects registration. The parent implementation trimmed this environment variable, so this commit regresses previously valid configurations such as LIBRECHAT_CODE_WORKER_DIR=' /srv/project '; return the normalized value for environment input while retaining the intended empty-value handling.

Useful? React with 👍 / 👎.

Fixed in 47d4832. Environment-provided worker directories are trimmed before empty-value normalization, preserving the prior behavior; CLI-provided paths retain their literal spelling. Added a CLI regression test with leading/trailing environment whitespace.

Remove the unsupported project-creation promise

When an operator follows this new workflow with an empty home, the registered workspace remains empty because LocalWorkspaceTools.capabilities in packages/code/src/workspace.ts only exposes read_file, search_text, and list_files; there is no operation that can create a directory or write a file. Consequently, bridge tools cannot create a project from scratch as documented here. Either add a write/create capability or state that the operator must seed the directory externally.

Useful? React with 👍 / 👎.

Fixed in 38d0d50. The documentation now explicitly states that the current workspace surface is read-only and an empty default directory must be populated by a local process until write-capable coding tools are enabled.

Namespace default workspaces by bridge identity

When the same host account re-pairs a worker ID for another tenant, this path remains identical because it includes only the public worker and workspace IDs. RedisBridgePairingStore.redeem creates a new stable identityId and tenant binding on every pairing, but the newly bound worker will advertise the previous identity's persisted files through read_file, search_text, and list_files; the same leak occurs when an ID is reused against another Code API deployment. Include the paired identity/deployment in the storage namespace, or explicitly clear the workspace when the security identity changes.

Useful? React with 👍 / 👎.

Fixed in 38d0d50. Default paths now include a deployment/security-identity namespace derived from the normalized Code API URL plus the paired public key (or static credential), ahead of the worker/workspace digests. Credential refresh within one pairing remains stable; re-pairing or changing deployments produces an isolated path. Tests cover both identity and deployment changes.